Whispergraph

@Whisper Security

20 days ago

# Security Internet Infrastructure Internet Measurement

The internet's largest queryable infrastructure graph — 7.39 billion nodes, 39 billion edges, 5.6 million threat-intelligence relationships. Pivot from any IP, domain, or ASN across DNS, BGP, WHOIS, GeoIP, and threat intel in a single Cypher query. Most threat-intel and OSINT APIs are point lookups: you ask about one indicator, you get one record. Investigations don't work that way — you start from one suspicious domain and need to trace its hosting, its sibling domains, its registrar, its email infrastructure, the ASN announcing its IP, and which feeds have flagged anything nearby. WhisperGraph stores all of that as a single connected graph and lets you traverse it natively. One query can answer questions that would take dozens of API calls anywhere else. Example questions you can ask **Is xyz-uknown@suspicious.com a safe email address? **What is the IP address of whisper.security? "What's the threat reputation of 45.142.213.55, and what feeds flagged it?" "Show every domain sharing this domain's MX records and registrant email." "Map the full DNS and BGP attack surface of example.com." "Which ASNs in Russia have the highest concentration of phishing-flagged IPs this quarter?" "Find all domains registered within 24 hours of suspicious-domain.com using the same registrar." "What's the historical WHOIS for disputed-domain.com going back 5 years?" "Which prefixes does AS13335 currently announce, and were any of them previously announced by a different ASN?"

概要ツールコメント

概要

This page walks you through connecting an MCP client to https://mcp.whisper.security. For the full surface (5 tools, 6 resources, 7 prompts) and example questions, see the MCP Reference.

Setup

Claude Desktop

Add it through Settings → Connectors:

Open Settings → Connectors
Click Add Connector
Enter the URL: https://mcp.whisper.security
Sign in with your Whisper Security account

Claude Code

claude mcp add --transport http whisper-graph https://mcp.whisper.security

Opens your browser for sign-in on first use. Scope options:

--scope user -- all projects
--scope project -- current project only
--scope local -- this machine, this project (default)

Cursor

Open Settings → MCP
Click Add new global MCP server
Paste:

{
  "mcpServers": {
    "whisper-graph": {
      "url": "https://mcp.whisper.security"
    }
  }
}

Save and restart Cursor For team-wide config, use .cursor/mcp.json in the project root instead.

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your project root:

{
  "servers": {
    "whisper-graph": {
      "type": "http",
      "url": "https://mcp.whisper.security"
    }
  }
}

For user-level config (all projects), use Command Palette > MCP: Add Server.

Windsurf

Open Settings (Cmd+, on Mac, Ctrl+, on Windows)
Search for MCP
Click View raw config
Add:

{
  "mcpServers": {
    "whisper-graph": {
      "serverUrl": "https://mcp.whisper.security"
    }
  }
}

Save and restart Windsurf uses serverUrl instead of url.

Antigravity

Click ... at the top of the chat panel
Click MCP Servers > Manage MCP Servers > View raw config
Add to mcp_config.json:

{
  "mcpServers": {
    "whisper-graph": {
      "serverUrl": "https://mcp.whisper.security"
    }
  }
}

Go back to Manage MCP Servers and click refresh Config file: ~/.gemini/antigravity/mcp_config.json

ChatGPT

Go to chatgpt.com → Settings → Connectors
Click Add Connector
Enter the URL: https://mcp.whisper.security
Complete the sign-in ChatGPT supports OAuth only.

OpenAI Codex

Add to ~/.codex/config.toml:

[mcp_servers.whisper-graph]
url = "https://mcp.whisper.security"

Then authenticate:

codex mcp login whisper-graph

Other clients

Any MCP client that speaks Streamable HTTP works.

Transport	URL
Streamable HTTP	`https://mcp.whisper.security`
SSE	`https://mcp.whisper.security/sse`
For STDIO-only clients, use the `mcp-remote` bridge:

npx mcp-remote https://mcp.whisper.security

Connecting through API key

If your client doesn't support OAuth, you can authenticate with an API key instead.

Go to console.whisper.security and generate an API key
Pass it as a Bearer token in the Authorization header

Most MCP clients let you set custom headers in their config. Add:

Authorization: Bearer YOUR_API_KEY

For STDIO-only clients, use the mcp-remote bridge with the --header flag:

npx mcp-remote https://mcp.whisper.security --header "Authorization: Bearer YOUR_API_KEY"

Keep your API key out of version control.

Validating your connection

Once the connector is registered, ask the assistant:

"List the WhisperGraph node labels."

The MCP client should invoke the list_labels tool and return roughly 20 labels (HOSTNAME, IPV4, IPV6, ASN, ANNOUNCED_PREFIX, FEED_SOURCE, …) with live counts. If you instead get an apology or a hand-written list of what the assistant thinks the schema looks like, the tool isn't connected — recheck the connector URL and re-authenticate.

Next steps

MCP Reference — every tool, resource, and prompt the connector exposes, plus example questions and the schema-introspection pattern AI agents should use before writing queries.
Cypher API Reference — if you'd rather call the graph directly over REST without MCP.

NextReference

Playgroundで試す

サーバー設定

{
  "mcpServers": {
    "whisper-graph": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.whisper.security",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Build with ShipAny.